|
|
Before you make any changes to Windows, bring up a working copy with the command line:
WIN /B
This causes Windows to write a file named BOOTLOG.TXT into the Windows directory. It also causes Windows to skip displaying the opening screen. As Windows concludes each step of its startup procedure, it writes a line in this file. Rename the file so it doesn't wind up being overwritten. Now, make your changes to Windows. If Windows fails to boot, you can tell how far it got before it failed, and by comparing the files, you can quickly narrow down the source of the problem.
Create multiple independent Windows setups by setting up your single-user computer like a network. When installing Windows, use the administrative option during setup: SETUP /A
.Windows will create a directory containing a mirror of all the files needed to perform a Windows installation, taking up 16MB to 18MB. When you've created this directory, you can run the standard or network version of Setup to install Windows. If you ever need a particular file or need to reinstall Windows, you can set up from this new directory.
You can run multiple versions of Windows without performing a full install each time. This allows you to test new software or hardware without messing up your normal production copy of Windows. First, create a mirror of the Windows installation disks.Then go to the DOS command line, make sure you're in the Windows directory and enter: SETUP /N
This will allow you to set up a new version of Windows, in a directory of your choice, with only the files needed to create a unique version. Repeat this command to create multiple, unique Windows directories. These new installations of Windows will share the files from the shared, adminstrative directory. You'll get clean copies of Windows without taking up the usual amount of disk space.
If you want to know all of your command line options for Windows setup, change to the Windows directory in DOS (usually CD \WINDOWS at the DOS command prompt) and type:
SETUP /?|More
The |More causes DOS to pause at the bottom of the first screen, since the description of Setup command line options takes more than one screen.
If you boot Windows and see only the "splash screen" at the start before the system locks up, or if your system returns to the DOS prompt without booting Program Manager, you probably have a driver problem, a hardware problem or a memory conflict. Try starting Windows with the command line: WIN /S
which will start Windows in Standard Mode. If Windows comes up, your installation problem is an enhanced mode problem. If that doesn't help, try editing your system files to remove your most recently installed drivers and see if Windows will boot.
Windows has a debug mode that can help you solve installation problems. If Windows won't run after you install it, try this command line: WIN /D:XSV
The D: means debug mode. The X means EMMEXCLUDE, which excludes the entire memory range occupied by adapters, such as network cards, sound boards or video cards--anything that uses shared memory. The S stands for SystemRomBreakPoint=Off, which keeps Windows from messing with the BIOS. The V means VirtualHDIRQ=Off, which tells Windows not to virtualize the hard disk. If entering one or more of these debug parameters makes Windows work, you can enter the appropriate command line permanently under the [386Enh] section in the SYSTEM.INI file.
If you check the Windows setup after an installation and Windows has misidentified your software, try again, typing: SETUP /I
This causes Windows to ignore detected hardware.
Windows knows the names of a number of programs with which it has difficulty. If you suspect you have a memory problem, try: WIN /T
When launched with this command line parameter, Windows searches the hard disk for memory-resident TSR (terminate and stay resident) programs and notifies you about certain programs known to cause trouble.
Video problems are the most common installation gremlins. If you can't get Windows running with your standard video driver, make a backup copy of SYSTEM.INI. Next, type SETUP
in the WINDOWS directory. Select either the VGA driver or the 8514 driver and attempt to start Windows again. If Program Manager appears, your problem was a video driver. Contact your video card manufacturer for an updated driver.
Here's how to track down memory problems. Make sure you have a bootable floppy disk. Rename CONFIG.SYS and AUTOEXEC.BAT on the hard disk. Create a new CONFIG.SYS with a single line:DEVICE=C:\DOS\HIMEM.SYS
Reboot your system. If Windows works, add back lines from your regular CONFIG.SYS file, one at a time, using NOTEPAD, then rebooting and entering WINDOWS again. Then add AUTOEXEC.BAT back in one line at a time. Continue this process until WINDOWS stops working. The last line you added is the culprit; work with customer support at the vendor involved and see if they can help you resolve the problem.
Sometimes, Windows will find your computer capable of 32-Bit Disk Access and 32-bit File Access when your PC isn't up to the task. This can prevent Windows from starting after installation. You can get Windows going by editing the [386enh] section of SYSTEM.INI. First, make a copy of SYSTEM.INI, then launch a text editor. In recent versions of DOS, there is a reasonably simple text editor called EDIT, usually found in the DOS directory. Older versions offer the difficult-to-use EDLIN program. Look for the line 32BitDiskAccess=ON. If you find it, put a semi-colon (;) in front of the line. This "comments it out," preventing SYSTEM.INI from executing that line. Then find the line Device=*WDCTRL, which activates 32-Bit File Access. Comment it out as well.
|
|